"202 Hack" is a shareware Java application which converts sequence information stored in standard MIDI files (SMF) into a format compatible with Roland MC-202(tm) sequences. Users have the capability to choose up to 2 MIDI channels (1-16) whose note information is extracted from the MIDI file and converted into the "internal" and/or "external" sequences of the 202. Accent and Portamento can also be coded as described below, as well as some post-processing tricks to generate "Roland TB-303(tm)-like" slides. The output of 202 Hack is an audio file (.wav format) which can then be played by your computer into the 202's "tape in" jack. The shareware fee for this program is $10 (U.S.), or you may choose to purchase an item from Defective Records instead. The author of 202 Hack co-owns this electronic dance music label.
HARDWARE / SOFTWARE REQUIREMENTS
- Any computer platform which supports the Java runtime environment can use 202 Hack. As of this time, this includes:
- Currently, 202 Hack requires the downloading and installation of the full Java runtime environment (e.g. Sun JDK 1.0.2, Apple MRJ 1.02 or 1.5, etc..). In the future, Java applications will be "bundle-able" so that no previous Java environments need to previously installed. Future versions of 202 Hack will incorporate this technology.
- Macintosh users automatically have audio output capability, so no extra audio output hardware is required. Windows and other platform users must have a soundcard installed.
- Finally some basic software is necessary to create a standard MIDI file, as well as to play a .wav audio file. There are several commercial, shareware, and freeware options for these two pieces of software for almost all platforms; as you've already shown enough interest in 202 Hack to read this far, chances are you've already got both software programs.
- You must have already downloaded and installed Sun's JDK 1.0.2 for this program to work. In the future, as Java tools progress, I may be able to create an executable file which will contain all needed code, but for now the Java runtime environment is necessary. Having Java-capable Netscape Navigator(tm) and/or MS Internet Explorer(tm) is NOT enough to run this program. JDK 1.0.2 is available at the following web site:
http://www.javasoft.com:80/products/jdk/1.0.2/index.html
- This software has NOT been tested yet with newer versions of the JDK, specificially 1.1.x.
- Be sure you have set the appropriate PATH and CLASSPATH variables for your Java runtime environment as described in the JDK documentation. IF YOU HAVE NOT SET THIS CORRECTLY, THE PROGRAM WILL NOT RUN. See Appendix 1 for more detailed instructions.
- Unzip the distribution file "202Hack101.zip". It should unzip into a folder called "202 Hack 1.01". Inside the folder, you should find the following files and folders:
202Hack.bat
manual202.htm (this document)
classes folder
test files folder
images folder
- You can move the 202 Hack 1.01 folder anywhere you'd like, but DO NOT RENAME OR MOVE THE classes FOLDER WITHIN IT.
- You must now update the CLASSPATH variable. THE PROGRAM WON'T RUN IF YOU DON'T DO THIS. Open your autoexec.bat file again as previously (NT users can go to control panels/system/environment variables) and add the following to the existing CLASSPATH:
;c:\wherever you put the 202 Hack 1.01 folder\202 Hack 1.01\classes
- Save the autoexec.bat file and reboot. NT users can just "apply" the changes without rebooting.
- You should now be able to double-click the 202 Hack.bat file to start the program. (On NT machines, the black command-line screen seen in the background may display a variety of Java "exceptions". These will not affect the operation of the program, and this will be fixed in later versions.) You can minimize (but not close) the black command-line screen which comes up in the background.
Macintosh (68040 or PowerPC processors):
- You must have already downloaded and installed the Java JDK 1.0.2 environment for this program to work. In the future, as Java tools progress, I may be able to create an executable file which will contain all needed code, but for now the Java runtime environment is necessary. Having Java-capable Netscape Navigator(tm) and/or MS Internet Explorer(tm) is NOT enough to run this program. The recommended Java environment at the current time is Apple's MRJ 1.51 environment. Download it from this web site:
http://applejava.apple.com/text/software.html
- NOTE: If you are operating under Macintosh OS 8.0 or greater, you should already have a sufficient version of Java on your machine, so there should be no need to download anything to get Java running. OS 8.0 comes bundled with MRJ 1.02 - this will definitely run 202 Hack adequately, however I *highly* recommend downloading MRJ 1.51, as it offers MUCH greater stability and speed over version 1.02.
- This software has NOT been tested yet with newer versions of the JDK, specificially 1.1.x. (This corresponds to MRJ 2.0, currently in beta as of this writing).
- Use Stuffit(tm) or similar utility to "un-binhex" the distribution file "202Hack101.sea.hqx".
- Double-click on the resulting self-extracting archive "202Hack101.sea".
- You will be left with a folder called 202 Hack 1.01. Inside the folder, you should find the following files and folders:
manual202.html (this document)
202 Hack
test files folder
images folder
- Double clicking the 202 Hack icon should start the program. Unlike previous releases of this software, you do not need to worry about ".class" files, JRunner, etc...
Windows 3.1: (infinite thanks go to Tim Hannigan, aka Mr. Spring, who helped me figure all this Windows 3.1 stuff out!)
- You must have already installed "PW1118.EXE", the Win32s 32-Bit add on for Windows / WFWG 3.1x. You can download it from here:
http://premium.microsoft.com/support/downloads/dp1219.asp
- You must have already downloaded and installed the Java JDK 1.0.2 for this program to work. In the future, as Java tools progress, I may be able to create an executable file which will contain all needed code, but for now the Java runtime environment is necessary. Having Java-capable Netscape Navigator(tm) and/or MS Internet Explorer(tm) is NOT enough to run this program. To install the Java environment, get "ADK for Win 3.1" from the following site, and follow its installation instructions:
http://www.alphaworks.ibm.com/
- Unzip the distribution file "202Hack.zip". It should unzip into a folder called "202Hack". Inside the folder, you should find the following files and folders:
manual.htm (this document)
classes folder
testfile folder
images folder
- You can move the 202Hack folder anywhere you'd like, but DO NOT RENAME OR MOVE THE classes FOLDER WITHIN IT.
- You must update the CLASSPATH variable. THE PROGRAM WON'T RUN IF YOU DON'T DO THIS. Open your c:\autoexec.bat file with any text editor, and add the following to the existing CLASSPATH:
;c:\wherever you put the 202Hack folder\202Hack\classes
- Save the autoexec.bat file and reboot.
- You launch 202 Hack using the ADK FILE utility; this is a File Manager style utility that will allow you to run Java code that uses extended filenames in Win 3.1x.
- If you look in your 202Hack directory from DOS or in File Manager, you will see several .CLA files in the \CLASSES directory. These appear as ".Class" Files When Seen In ADK FILE, and it`s these ".Class" files that you double click on to start a Java application running.
- Run ADK FILE, and find the directory you unzipped the 202 Hack code into (usually :\202Hack). Look in the "Classes" Directory within it, and double click on the file "Hack202.Class". This should start 202 Hack running!
- NOTE: If you forget to select a track in your .MID to make a .WAV of (i.e. if you leave both Internal and External as "None"), 202 Hack will hang your machine. This is a Java bug on this platform.
SPARC/Solaris 2.3, 2.4, 2.5 and X86 Solaris 2.5:
- You must have already downloaded and installed Sun's JDK 1.0.2 for this program to work. In the future, as Java tools progress, I may be able to create an executable file which will contain all needed code, but for now the Java runtime environment is necessary. Java-capable Netscape Navigator(tm) and/or MS Internet Explorer(tm) is NOT enough to run this program. JDK 1.0.2 is available at the following web site:
http://www.javasoft.com:80/products/jdk/1.0.2/index.html
- Be sure you have set the appropriate PATH and CLASSPATH variables for your Java runtime environment as described in the JDK documentation. IF YOU HAVE NOT SET THIS CORRECTLY, THE PROGRAM WILL NOT RUN. See Appendix 1 for more detailed instructions.
- Now follow remainder of directions as for Windows95.
- 202 Hack has not been tested yet on this platform.
- Check the following web site for updates on Java runtime environments for your platform; new ones are being created quickly (BeOS, NeXT, Amiga, Digital UNIX, Silicon Graphics, etc), and this software should work unmodified on all of them:
http://www.javasoft.com:80/products/jdk/jdk-ports.html
202 Hack takes a standard MIDI file input and creates a .wav file as an output. This .wav file can then be "played" by your computer into the tape in jack on your MC-202(tm) to transfer the sequence information from your MIDI file into the 202's sequencer. I leave it to you to figure out what set of plugs and cables you'll need to connect the computer to the MC-202(tm) ; it's pretty straightforward.
202 Hack works with both type 0 and type 1 MIDI files; it does NOT work with type 2 files, so you will need to convert those to type 1 files if you'd like to process them. There are several easily available utilities to help you do that if need be.
MIDI running status is supported, as some sequencers output MIDI files in this format. If you have no idea what running status is, don't worry about it! It just means that 202 Hack is able to process all types of MIDI files.
Click on the "Browse" button to select the input MIDI file to process. If you prefer to type in your own, you must type in the complete path and name of the file.
202 Hack automatically will strip the ".mid" or ".MID" extension from your file, and replace it with a ".wav" extension. If your MIDI file does NOT end in ".mid", then 202 Hack just adds on the ".wav" extension to the existing file name. You can rename the output .wav file manually by just typing in your preferred name in the "Output File" box.
202 Hack automatically places the created .wav file in the same directory as the original MIDI file. If you prefer to place it elsewhere, you must type in your preferred directory manually.
202 Hack will currently NOT overwrite an existing file (it displays
an error message if you try). This will be changed in the future to allow
for a user-selectable preference to allow for either automatic file overwriting
or accept/reject dialog box prompt for overwriting.
back to top
The MC-202(tm) has provision for 2 stored sequences, the "internal" and "external" sequences. The "Int Seq" and "Ext Seq" popup menus allow you to select which MIDI channels from the input MIDI file will be mapped to the internal and external sequences, respectively.
You MUST specify at least one of these popups to be a value other than "None" for 202 Hack to work. The range of accepted MIDI channels is 1-16.
There are two ways that you can specify Portamento with 202 Hack:
1. Since the MC-202(tm) is monophonic, two notes on the same MIDI channel which overlap one another in the original MIDI file will not translate exactly when moved into 202 sequencer-land. If 202 Hack does encounter two overlapping notes, it will truncate the first note at the time the second note starts. If the "Overlapping Slide" popup is in "No Slide" mode, then NO portamento is coded for either note. If "Overlapping Slide" is in either "Normal Slide" or "303-ish Slide" mode, then portamento will be coded as described below.
2. 202 Hack will also code for portamento on a particular note if it reads pitch wheel controller data while the note is on. Practically what this means is that you can just twiddle the pitch wheel a bit while recording your sequences at the moment that you want a note to be portamento'd. Alternatively, you can manually enter pitch wheel controller data in your sequencer after you've recorded your sequence notes. It makes no difference whether the pitch wheel is moved up or down; the portamento is coded the same way into the 202 sequence. This method of coding for portamento is independent of the "Overlapping Slide" popup.
"Normal Slide" mode will specify Porta on the second of two overlapping notes. This will create a slide from the first note to the second note.
"303-ish Slide" implements a trick nicely described by Rob Joyner at the excellent MC-202 web site run by Shawn Mativetsky, http://www.citenet.net/noise/202/. It basically adds what Rob coined "slide premonition" to 2 overlapping notes, to simulate the 303 effect of sliding to a new note before the last one's finished sounding. So if, for example, C2 and C3 are overlapping in your original MIDI file, and "303-ish Slide" is active, you'll get an output MC-202 sequence something like this:
| Pitch | C2 | B2 | C3 |
| Step | 11 | 01p | 12p |
| Gate | 11 | 01 | 06 |
There are several user-selectable preferences for this mode, accessible by clicking the button called "303 Slide Prefs". This button is inactivated when the "Overlapping Slide" popup is in either of the other two modes, "No Slide" or "Normal Slide". The preferences are all for the "premonition note" (in our example above, the premonition note is the B2). There are three values that can be adjusted: offset, length, and accent.
The offset of the premonition note can be modified in integer steps (positive or negative). So if the offset was set to 2 in our example above, the new premonition note would be A#2, as it is two steps away from C3. The default offset value is 1. All positive values for the offset will cause premonition notes to be between the 2 overlapped notes; negative values cause the premonition note to be further away from note 1 than note 2 is. The following examples should clarify things:
| Offset = 1 | |||
| Pitch | C3 | C#2 | C2 |
| Step | 11 | 01p | 12p |
| Gate | 11 | 01 | 06 |
| Offset = -1 | |||
| Pitch | C3 | B1 | C2 |
| Step | 11 | 01p | 12p |
| Gate | 11 | 01 | 06 |
| Offset = -2 | |||
| Pitch | C2 | D3 | C3 |
| Step | 11 | 01p | 12p |
| Gate | 11 | 01 | 06 |
| Length = 3, Offset = 2 | |||
| Pitch | C2 | A#2 | C3 |
| Step | 09 | 03p | 12p |
| Gate | 09 | 03 | 06 |
| Length = 3, Offset = 2, Accent = On | |||
| Pitch | C2 | A#2 | C3 |
| Step | 09 | 03p,a | 12p |
| Gate | 09 | 03 | 06 |
202 Hack will create an accented note if it reads specific MIDI controller or velocity messages while a note is on. The exact way that accent data is coded is specified by the status of the "Accent Control" popup. The available options are No Accent, Velocity, Mod Wheel, or Volume (MIDI controller #7).
If you choose "No Accent", then no accented notes will be coded for at all. If you choose "Velocity", then 202 Hack will accent notes that have velocities greater than the Threshold parameter. The default for the Threshold parameter is 100; you can change it to any value between 0 and 127. If you choose 0, then all notes will be accented; choosing 127 will cause no notes to be accented, effectively the same as choosing the "No Accent" mode. The Threshold parameter has no effect when using the other Accent modes, and this is indicated by a "N/A" in its box.
Choosing either "Mod Wheel" or "Volume (MIDI controller #7)" will cause 202 Hack to code for accented notes if it senses either of these MIDI controller messages while a note is already playing. Practically what this means is that you can just twiddle the mod wheel a bit while recording your sequences at the moment that you want a note to be accented. Alternatively, you can manually enter mod wheel or volume controller data in your sequencer after you've recorded your sequence notes. It makes no difference whether the mod wheel or volume is moved up or down; the accent is coded the same way into the 202 sequence.
Press the "Process" button to start the conversion. In most cases, the conversion will be so fast that you won't see the little "Working?" message that comes up between the "Process" and "Quit" buttons, but on long files you will see that status message. If you've specified an invalid file, not specified a MIDI channel, or specified an invalid velocity threshold (when applicable), you will be prompted with a dialog warning box.
You can keep the program open and in the background while trying out your new .wav file in your MC-202(tm). If you want to try again, no need to restart the program, just click browse to specify a new file to process, and then click "Process" again.
Uhh, press the "Quit" button.
- This program has been tested only with Java JDK 1.0.2. It may work fine with JDK 1.1.x but this has not been tested yet.
- The output .wav file is a mono, 22.050 kHz, 8 bit, unsigned file.
- PC users may get bizarre colors or no colors displayed when in 256 color mode. Switching to a higher color mode fixes this. This is a known Java bug, and should be fixed in later releases of Java.
- Currently, 202 Hack will not process a MIDI file correctly if both internal and external MIDI channels are set to the same value. Only the internal sequence will be coded for.
- On the Windows 3.1 platform, if you forget to select a track in your .MID to make a .WAV of (i.e. if you leave both Internal and External as "None"), 202 Hack will lock up your machine. This is a Java bug on this platform.
Q: How did you get Roland to give you the MC-202's(tm) sequencer format code?
A: I didn't. I figured out the code myself - see next question...
Q: How did you do it???
A: I first had to figure out the MC-202's(tm) sequencer format. I did this by "reverse engineering". What this means is that I created literally hundreds of simple sample sequences on the MC-202(tm), and then dumped the tape audio output into my computer (a PowerMac 7100/66, if you must know). Using a visual audio editor on the computer, I analyzed the waveforms, comparing the outputs from sequences that differed in only one parameter at a time. By repeating this process over and over, I gradually figured out how the MC-202(tm) coded for its sequences.
I then had to learn the Standard MIDI File format, and write the computer code to convert the note information stored in a MIDI sequence into the format that the MC-202(tm) understands. Finally, I had to learn the .wav File Format, and create and output the appropriate audio file.
Q: Why Java?
A: Java enables the same computer program to be executable by almost all major computer platforms on the market at this time. I personally was tired of seeing applications released that looked great, only to be disappointed later to find out that they were not available for my platform. I didn't want 202 Hack to fall into the same category, and it's my hope that others will follow this path in the future!
Q: Why did you use MIDI files, rather than just create a graphical note interface like other sequencing programs?
A: I'm not a professional computer programmer by any means; investing the time and energy into created a complex graphical interface would have really hindered the development of this program. I had my hands full as it is! Furthermore, since almost everyone already has a sequencer capable of outputting standard MIDI files, I thought that this would be a reasonable route to go. Finally, Java is still a young computer language (active use slightly more than one year), and it's graphical tools are still fairly immature. In addition, graphics appear slightly different on each platform, and would be hard to control for.
Q: Why is it so boring to look at? Why doesn't it look slicker? Why the ugly colors?
A: Several reasons here: 1) As mentioned above, Java is still in it's infancy, and graphical development tools are not as nice as they ought to be. It's a PAIN to make things look nice in Java right now. 2) Point #1 is partly because of Java's working on multiple platforms - things don't always come out looking the same in different operating environments, so it's a waste of time to "tweak" your layout too much to make it look pretty, because it's going to be different on the next computer you try it on. 3) I'm really *not* a computer programmer by profession, and I struggled enough just getting the guts of the program to work, let alone make it look slick. Personally I'd rather keep adding cool features, rather than make it look like some commercial piece of software!
Q: What's all this about Defective Records?
A: Defective Records is an electronic dance music label that I co-own and run, together with my long time friend and co-DJ, Bump Stadelman. I wanted to increase the awareness of people in the electronic music community to the label, as I really think we offer some unique sounds not available elsewhere. Buying a Defective product and having the Defective web site host 202 Hack seemed like a nice way to do just that. I hope you agree!
BUG REPORTS / SUGGESTIONS / CONTACTING ME
- Please send in ALL bug reports, with as much info as possible: platform, Java environment, MIDI file (supplying the actual MIDI file is ideal), internal and external MIDI channels, slide mode setting, accent controller setting, threshold parameter, and a detailed description of the problem. I've set up the following web-based bulletin board to enhance communication between everyone re: the programs development, questions, answers, etc...
http://www.greenspun.com/bboard/main-frame.tcl?topic=Roland%20MC-202%20Hack
- Suggestions for enhancing the program are also welcome, so feel free to post them to the above bulletin board.
- I'm obviously also available by direct e-mail at the address below, but any questions, bugs, tips, suggestions, etc.. should go to the b-board. This will help eliminate identical questions, and serve as a great repository of information for other users.
- The 202 Hack "official" web site will be maintained at the Defective Records web site:
http://www.welch.jhu.edu/~geh/defective.html
- If you're interested in obtaining the MC-202(tm) tape format scheme which I reverse engineered for one of your own applications, please contact me directly.
Dan Nigrin
dnigrin@welchlink.welch.jhu.edu
REGISTERING / PAYING YOUR SHAREWARE FEE
- The shareware price for this program is $10, payable by cash, US personal check, or international money order to Dan Nigrin. Mail it to:
Dan Nigrin
178 Tappan St.
Brookline, MA 02146
USA
- Alternatively, you can purchase at least one item via mail order from Defective Records, the electronic dance music record label I co-own/operate. Visit our web site at
http://www.welch.jhu.edu/~geh/defective.html
for more info. A printable order form is there, as well as specific ordering instructions and prices. Please note that record/CD orders are mailed to the Defective Records address listed on the web site, and NOT to the address above. Also, AND VERY IMPORTANT, you MUST write "FOR 202 HACK" in big letters on your order form to get credit as a 202 Hack user and for full registration. Omission of this will fail to get you your 202 Hack registration, NO EXCEPTIONS!
- Paying the shareware fee or buying a Defective product (!) entitles you to all future upgrades and enhancements to 202 Hack at no charge, as long as you can receive electronic delivery of the program. Floppy disk delivery will incur an extra charge. Also, registered users will get as much user support (via e-mail only) as I'm able to give.
- This program is not free, and should not be distributed to anyone. A registered user may make as many copies for him/herself as often as they would like.
- I hold the copyright, publishing, patent, trademark and whatever other "rights" you would like to name. If you try to steal this program from me, I will have to hurt you.
APPENDIX 1 - Java installation Windows95/NT
-----------------------------------------------------------------------
WINDOWS PATH and CLASSPATH
-----------------------------------------------------------------------
After installing the software, update the PATH and CLASSPATH as follows.
Windows NT only - If you are using Windows NT you can instead make the following environment variable changes in the Control Panel. Start the Control Panel, select System, then edit the environment variables.
1. PATH - Add the following directory to your path:
JAVA\BIN
The PATH statement enables Windows to find the executables (javac, java, javadoc, etc.) from any current directory.
To change the PATH, open the AUTOEXEC.BAT file and make the change to the path statement. To edit the AUTOEXEC.BAT file in Windows 95:
i. Start a text editor by choosing "Start", "Programs", "Accessories", and choosing WordPad or NotePad.
ii. Choose Open from the File menu and type "c:\autoexec.bat" for the filename This will open the file for editing.
iii. Look for the PATH statement. Notice that the PATH statement is a series of directories separated by semi-colons (;). Windows looks for programs in the PATH directories in order, from left to right. When in doubt, put the java directory at the end of the path statement. For example, in the following PATH statement, we have added the java directory at the end:
PATH C:\WINDOWS;C:\WINDOWS\COMMAND;C:\;C:\DOS;C:\JAVA\BIN
2. CLASSPATH Environment Variable - Edit the AUTOEXEC.BAT file (as in the previous instructions) and set the CLASSPATH environment variable to the current directory (.) and the directory containing the Java Core Class library file, known as CLASSES.ZIP. Separate directories by semi-colons.
SET CLASSPATH=.;C:\JAVA\LIB\CLASSES.ZIP
The CLASSPATH tells Java applications where to look for the CLASSES.ZIP file, which is the Java Core Class library.
See the Troubleshooting section that follows for more information.
3. Reboot - After completing these changes to AUTOEXEC.BAT, save the file and reboot, to make the changes take effect.
-----------------------------------------------------------------------
WINDOWS INSTALLATION TROUBLESHOOTING
-----------------------------------------------------------------------
Here are some troubleshooting tips for Windows:
* Error Message: Exception in thread NULL
If you are getting the fatal error message: Exception in thread NULL, when running java, javac, or appletviewer, you should check your CLASSPATH environment variable. It may list the 'classes' directory from an older JDK release. You can either unset the CLASSPATH variable, or set it to include only the latest version of the JDK class library. For example:
C:\> set CLASSPATH=.;C:\java\lib\classes.zip
This will make sure that you are using the correct classes for this release.
* Cannot close AppletViewer copyright window (Windows 95 only)
In Microsoft Windows 95, the launch bar may partially cover the AppletViewer copyright notice window Accept and Reject buttons. If this happens, you can move the Windows 95 launch bar to the side of the desktop to allow access to the copyright window Accept and Reject buttons.
APPENDIX 2 - Java installation SOLARIS
-----------------------------------------------------------------------
SOLARIS PATH and CLASSPATH
-----------------------------------------------------------------------
After installing the software, update the PATH and CLASSPATH variables as follows.
1. path - Add the following directory to the Unix path variable:
java/bin
If you use the C shell (csh), you can do this by adding that path to your path variable in your .cshrc file.
2. CLASSPATH - You must set the CLASSPATH entry to point to "java/lib/classes.zip". You can do this by opening the .cshrc file and making the change to the CLASSPATH environment variable. See the Troubleshooting section below for more information.
After completing these changes to .cshrc, save the file and execute the following to make the changes take effect:
% source .cshrc
-----------------------------------------------------------------------
SOLARIS INSTALLATION TROUBLESHOOTING
-----------------------------------------------------------------------
* Error Message: Exception in thread NULL
If you are getting the fatal error message: Exception in thread NULL, when running java, javac, or appletviewer, you should check your CLASSPATH environment variable. It may list the 'classes' directory from an older JDK release. You can either unset the CLASSPATH variable, or set it to include only the latest version of the JDK class library. For example:
% setenv CLASSPATH .:/usr/local/java/lib/classes.zip
This will ensure that you are using the correct classes for this release.
2/23/97: Alpha 1.0 version release
2/27/97: Alpha 1.1 version release
- added MIDI running status support.
- added ability to read note off events that are coded by MIDI note ON events with velocity of zero.
- fixed input/output file problem that added extra "/" between directory and file.
- added ability to strip ".MID" from filename before adding .wav ; previously, only recognized ".mid".
- improved Mac distribution package to allow for simpler execution.
2/28/97: Beta 1.0 version release
- revised this document.
3/3/97: Beta 1.1 version release
- 202 Hack now "releases" .wav file as soon as it's created, allowing .wav player programs access to file without having to quit 202 Hack first. This was a problem only for W95/NT users.
- fixed problem with .wav file header which was causing W95/NT .wav players to misread length of .wav file and/or say file was corrupted.
3/22/97: Beta 1.2 version release
- made leader tone significantly longer.
- added "No Accent" choice to Accent Control popup.
- added "Velocity" choice to Accent Control popup. Also added "Threshold" data entry box, so that a threshold can be entered by the user when using the Accent Control via Velocity.
- fixed and enhanced "303-ish Slide" mode. Added ability to modify preferences for how the note premonition is done (amount of note premonition offset, length, and whether to accent or not).
- fixed .wav file output so that W95/NT audio file players immediately recognize the file as a .wav, not a generic PCM file. This means that MS MediaPlayer can play the .wav files now.
- changed error notification to standard dialog boxes, rather than output to Java "stdout".
- updated this document, and converted it into HTML form.
3/31/97: 1.0 version release
- fixed "browse" button to remember the last directory user was in.
- added popup menu alerting user if MIDI channels are chosen for which no data exists on the selected .mid file. In this case, no .wav output file is created.
- updated this document again.
11/9/97: 1.01 version release
- fixed Windows 3.1 distribution package, to account for 8+3 filename restriction, and to integrate better with ADK tools.
- updated Mac distribution package - no class files, JRunner, etc. are necessary now. A single double-clickable file is all that is distributed.
- package sample MIDI and .WAV files with each distribution package to allow users to test audio connection between computer and 202, to be sure that aspect of their system is working OK.
- updated this document, updated web site.